Skip to main content

Known use case for Single System connection

The Single System connections are built based on the concept of Windows child session, which is a special loopback Remote Desktop Protocol (RDP) session that is tied to a user's existing session. Refer Windows Child Session.

With the basic concept of Windows child sessions, certain known use cases and expected behaviors arise when dealing with a Single System connection in an SUT (System Under Test). Below are some known use cases or issues for Single system connections.

Known issues: The SUT viewer window shows a black screen the first time you launch a Single System connection​

Issue: When you connect the first time, you might see a black screen.

Fix: Re-connecting will resolve this issue.

Known issue: Browser application unable to launch without creating a new profile​

Issue: You cannot launch Google Chrome simultaneously from both the parent machine and the SUT because Windows restricts the launch of Chrome using the same profile between the parent session and the child SUT.

Fix: Create a new profile for Chrome, and launch it from the SUT.

Known use case: Single System connections cannot run as Windows services​

Use case: Single System connections are not workable when they are initiated from a Windows service because services run in a non-interactive session, which lacks access to user sessions. This prevents GUI interactions, remote desktop protocol (RDP) connections, and certain authentication mechanisms from functioning properly.

Fix: Enable a Windows child session from a Windows service by configuring the service to run under a specific user account instead of the default local system account. This allows the service to operate within an interactive user session, enabling GUI interactions and resolving limitations related to session isolation.

Known use case: User account for Single System logon​

  • Single System connections must run under the same user account as its parent session (which is Eggplant Gateway/EPF installed) to inherit the necessary permissions, environment variables, and interactive session context.
  • If a different account is used, the child session may face access restrictions, GUI limitations, or authentication failures.

Known use case: User account access permission for Single System logon​

  • Single System connections requires the user account to have at least the below access permissions:
    • The user account must belong to the Administrator group.
    • The test machine must have Remote Desktop Services enabled.
    • The user account must be added to the Remote Desktop User Group.
    • Eggplant Gateway CommandLine Interface (CLI) provides commands to help set up user accounts with some permission access, except Administrator. For Administrator access, you should work with your IT personnel for assistance.
      • Run the command below (with Administrator mode) to set up user account permissions:
        • cd {path where the eggplant gateway located}
        • ./epgw setup single-system
note

This command also runs when you install Eggplant Functional.

Last updated on